User Management
SCS does not require a login for all of it's functions, for instance if templates are shared appropriately then users can run them without having to log in. However, many operations inside SCS require the user to be authenticated before allowing them to be performed. Any action which is tied to an account, such as creating or editing templates/widgets/layouts require authentication. Building Custom Messages, participating in Events, etc all require the user to have an active account before they can proceed.
Users cannot self-register, an administrator must approve and create them an account. This is done via the Manage Users link under the System menu item.
The main grid presents the list of users currently registered to use your local SCS system. You can click on the column headers to sort by their content (so you can quickly see which accounts haven't been logged into in a while, which have admin rights, etc).
Users who haven't logged in will be highlighted in red such as "new.user" below
To create a new user simply click the +Create New User button located in the upper left corner of the grid.
If you want the account to be automatically locked out of SCS for security reasons (such as if they enter the wrong password to many times in a row) be sure to check the Can Lockout checkbox.
There are two main roles available to new users, very few will be Administrators, most will be scientists.
If you grant admin rights to the new account be aware it will have the same rights you currently do and full admin access to all of the system.
On the main grid, at the end of each row is a set of buttons which allow you to perform actions on the given user's account. Some of the changes might require the user to log out and then log back in before they will take effect.
If you delete an account all templates assigned to it will be re-assigned to you. Deleting an account cannot be undone!
When editing a user you may notice you cannot change some of the things initially specified when creating their account. You'll also notice you can specify some additional fine-grain privileges such as granting a non-admin account semi-admin rights in certain subsections of SCS. For instance you can allow an account in the Scientist role to have full admin rights in the QA/QC subsystem inside SCS. This user can not do general admin duties, such as modify CFE or create new users, but they CAN now create, update and delete QA/QC definitions which a normal scientist account can not do.
